ci(release): announce releases in repo and org discussions#167
Open
rahlk wants to merge 1 commit into
Open
Conversation
- repo-level: add discussion_category_name + discussions:write permission so action-gh-release opens an Announcements discussion linked to the release - org-level: new createDiscussion step posting the same body to codellm-devkit/.github, authenticated by ORG_DISCUSSIONS_TOKEN (continue-on-error) - bump version 2.4.1 -> 2.4.2 so a release can exercise it Closes #166
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #166.
What
Post each release to GitHub Discussions in two places (parity with
codeanalyzer-typescript/-python):discussion_category_name: Announcementsto the existingaction-gh-release@v3publish step, plusdiscussions: writeto the workflowpermissions:block (the restrictive block otherwise denies the release-linked discussion with a misleading "valid category name" error). Seeded from the composedrelease-notes.md.continue-on-errorstep posting the same body intocodellm-devkit/.github→ Announcements via acreateDiscussionGraphQL mutation, authenticated byORG_DISCUSSIONS_TOKEN.Also bumps
gradle.properties2.4.1 → 2.4.2so the next tag actually exercises this.Prerequisites (already done)
Announcementscategory on this repo.ORG_DISCUSSIONS_TOKENhasreposcope.